If you were using GG version 1.xx, some of this will be completely irrelevant to
you as many of the changes only refer to version 2 users, although you should
still read this file to be on the safe side. You can of course ignore this file
and start again from scratch.
Part of this file is in BTD.DOC. If we've missed anything, please let us know.
BTD.COM is a COMPLETELY REWRITTEN version of GG.EXE. Instead of using Turbo C,
we've used TASM 2.0 to produce the code. This makes it faster to load, quicker
to run and allows us to pack more features into a much smaller space. We've had
to change quite a lot though, mainly to make BTD more compatible with similar
products, but also to add new features. The original GG.EXE program was getting
a bit unwieldy, even after rewriting it for version 2.00!!!!
Because of these changes, registered users of any GG version can upgrade FREE.
You should call us on the usual phone numbers if you want a copy, or if you have
ANY problems converting from GG to BTD. GG.EXE is no longer available.
IMPORTANT NOTES FOR GG.EXE USERS UPGRADING TO BTDIMPORTANT NOTES FOR GG.EXE USERS UPGRADING TO BTDIMPORTANT NOTES FOR GG.EXE USERS UPGRADING TO BTD___________________________________________________________________________________________________________________________________________________
The biggest difference between BTD and GG is the size of the executable file. GG
v2 was a massive 27618 bytes and with the sole exception of the limited callback
feature, GG version 2.00 had few extra functions - and ran a lot slower...
Our initial targets for BTD v3 were to use 1024 bytes or less when spawning and
to have an executable under 8192 bytes. We did it, on time and with a little bit
of room to spare.
The full list of GG versions are as follows: 1.00, 1.01, 1.10, 1.20, 1.40, 2.00,
2.01, 2.02, 2.10, 2.20 and 2.30. Version 1.30 was a special one-off version.
1) The /C (Callback) switch is not supported by BTD and is ignored if found on
the command line. (Only 1 registered GG user employed it anyway!)
2) The midnight event can longer be cancelled. BTD does not store the config
information in separate file and needs it to process the next day's events.
3) The H (hourly) event type prefix is no longer supported. BTD's new method of
setting event times means that it is no longer required. On the other hand,
you now get the choice between USER and NON-USER events without having to
select errorlevels. See page 13 of the BTD manual for full details.
4) BTD has more errorlevels available for events, although this might change
with the imminent release of Maximus 2.00. GG used errorlevels 41 to 230
while BTD uses 30 to 239.
5) ALL BTD's events are now affected by the MINTIME setting. Using errorlevels
220 to 230 are now handled in the same way as the others.
6) Events no longer have to be in time order. BTD will now sort them for you.
7) Modem and text strings are no longer surrounded by quotes. If you don't want
quotes to be sent to the modem/caller, remove them from your strings.
8) The modem delay and DTR control characters ('"v^, etc) are no longer needed
and will now be sent to the modem as they are not translated. BTD now tries
to handle the appropriate delays internally.
9) The @ file identifier for banners is not currently supported. It may return
in a future version if anyone wants it. Sorry, it wasn't on our list for
things to add to this release. (Don't know how we missed it!!?? Tony:)
10) The SYSOPEN and SYSCLOSE system times verbs in v1.20 and later have now been
replaced with SYSTIME. Version 2.10 and later had this as an alternative.
11) Creating a BBS.BAT file is no longer an option. GG v1.xx users should note
that this was their ONLY option. Version 2.xx users should note that using
EXIT 2 will cause an error to be reported and BTD will spawn the BBS.
12) The callback verbs (RETRY, DIALPREFIX and CALLDATA etc) used in v2.xx are no
longer supported. BTD doesn't have a callback facility.
13) The following verbs are not supported as BTD does not change directory while
running: GGDIR, BBSDIR, LOGDIR and CFGDIR.
14) The GGLOG verb has been replaced with LOG. BBSLOG remains the same.
15) Version 1.00's PORT command is no longer 0 (zero) based (0 for COM1 etc).
This was changed in version 1.01.
16) Placing a 0 (zero) in front of the port number will no longer force it to be
zero based (v1.01 to v1.30 only).
17) Modem strings have changed size to either 38 and 78, rather than 30 and 40.
18) Text strings are now 78 instead of 158.
19) All file spec verbs now allow the path to be included. (The LOGDIR verb etc
is no longer supported.)
20) File spec lengths are now 72 instead of 60.
21) The password option for Sysop access when the system was closed has been
removed. This applies to registered 2.30 users only.
22) The number of events is now 100. Up from 20 in v1.00 to v1.20, and up from
40 in all versions except v2.10 and 2.20 which also had a maximum of 100.
23) Multiple opening and closing times are no longer supported. Version 2 users
should note that although GG didn't allow times to span midnight, BTD does.
24) All the defaults except the baud rate and comms parameters have changed. See
page 8 of the BTD manual for the new settings.
25) Version 2's /G command line switch, which invoked v1.xx file compatibility,
is not supported. BTD only uses a slimmed down version of the SCH file (now
called SCD).
26) The /D command line switch which forced the use of the internal defaults is
not supported. Use an empty configuration file to use only BTD's defaults.
27) The position of the log file verb in GG's config file is now irrelevant. BTD
will not open the log file until AFTER the config file has been parsed.
28) BTD uses only 1 file, BTDnn.SCD where nn is the task number. Please delete
your existing GGnn.GCS (callback settings) GGnn.GSS (system settings) and
GGnn.SCH (schedule) files. You could of course leave them, but BTD won't use
them and they'll take up valuable hard disk space for no purpose.
29) Using the command line /N switch for the task number is no longer supported.
All the task number settings, except when creating the new SCD file, must be
done in the CFG file.
30) Unlike GG, BTD will not automatically add the task number to its own and the
BBS log file name. If you want to maintain this ability, you'll have to do
it manually in the config file.
31) Version 2.xx users should note that BTD does not support hexadecimal task
numbering. Only DECIMAL numbers 0 to 99 are now supported.
32) BTD always uses a task number when spawning. This was decided at an early
stage in BTD's v3.00's development as it was felt to be more consistent when
multiple lines are in use.
33) When logging on locally via the spawn, BTD always uses a task number.
34) If you've lost or deleted your original configuration files, start GG with
the /S (show) switch followed by the /N (task) switch to list the contents
of the GCS, GSS and SCH files. Version 2 users can redirect the output to a
file or printer instead of the screen. Version 1 users will have to use
print screen to get a hard copy of the information.
After making your changes, the configuration file should run without any further
